Release 10.1A: OpenEdge Development:
AppBuilder

Basic pushbuttons

In a GUI, a pushbutton is equivalent in power and generality to a menu item. Indeed, you can construe a pushbutton as being a self-contained, single-item menu. Since pushbuttons are normally always visible, they offer more immediacy and convenience than menu items at the cost of taking up more space. Because they do take up more space, you will probably want to use them sparingly.

Because of how they are used in everyday life, pushbuttons in a GUI are associated with invocations, actions, and major state changes, not with minor state changes such as setting a single value. Using them in a way that runs counter to this expectation can make your applications harder and less satisfying for people to use.

AppBuilder supplies a default, undefined pushbutton object as well as a number of pushbuttons preconfigured for common applications:

View page — Applies only to ADM paging (see the "Simple SmartContainers" section). Causes objects associated with a certain page number to appear. You supply the number as an argument to the call in the trigger code. Already-visible objects assigned to other ADM pages do not disappear.
OK, Cancel — Accepts/discards changes and closes the parent dialog box or window.
Done — Calls the application’s shutdown routine.
Help — Calls the help system.
First, Prev, Next, Last — Moves the current-record cursor to the record indicated by the button.
Custom Size/Color — (Default) Creates a generic pushbutton with no action defined on it. You must add the action code yourself in the CHOOSE trigger.